Open topic with navigation

Release Team

In Digital.ai Release, a release represents a number of activities in a certain time period. Digital.ai Release is used to plan, track, and execute releases automatically. Each release or release template defines a set of teams. For example, you can have a Development team, a QA team, a Delivery Team - all working in a single release.

Release Team iCube enables you to create ad hoc reports to help you in analyzing your releases and release cycles. It provides valuable Release Analytics to help you gain better understanding of the operational efficiency of your releases. You can gain valuable insights into risk elements, percentage of overdue releases, causes for delays, compliance, time efficiency, and so on.

Attributes

Expand this link to view the list of attributes available as part of the Release Team iCube:

Attributes	Description
Calendar Date	Gregorian calendar date displayed in the format 'M/D/YYYY'
Calendar Month	Gregorian calendar month displayed in the format 'Mon YYYY'
Calendar Quarter	Gregorian calendar quarter displayed in the format 'Q# YYYY'
Calendar Week	Gregorian calendar week displaying the week number. For example, W21, W22.
Calendar Year	Gregorian calendar year displayed in the format YYYY
Date	Date on which the release is due
Lagging Count of Days	Count of number of days since the first data record till current day (where current day is taken as 0)
Lagging Count of Months	Count of number of months since the first data record till current month (where current month is taken as 0)
Lagging Count of Quarters	Count of number of quarters since the first data record till current quarter (where current quarter is taken as 0)
Lagging Count of Weeks	Count of number of weeks since the first data record till current week (where current week is taken as 0)
Lagging Count of Years	Count of number of years since the first data record till current year (where current year is taken as 0)
Release ID	Unique ID of the release
Release Name	Name of the release
Team	Name of the team working on the release

Metrics

Expand this link to view the list of metrics available as part of the Release Team iCube:

Metric Name	Description	Formula	Expected Value
% Completed Within Time Release Tasks	Percentage of releases that are completed within the planned and due time of the release	NullToZero(([No of Completed Within Time Release Tasks] / [No of Completed Release Tasks]))	Higher value is ideal
% Completed Within Time Releases By Team	Percentage of releases that are completed within the planned and due time of the release associated to a team, where the team has worked on tasks for a release	NullToZero(([No of Completed Within Time Releases by Team] / [No of Releases by Team]))	Higher value is ideal
% High Risk Releases by Team	Percentage of releases with high risks associated to a team, where the team has worked on tasks for a release	NullToZero(([No of High Risk Releases by Team] / [No of Releases by Team]))	>=0
% Overdue Release Tasks	Percentage of all overdue tasks associated with a release	NullToZero(([No of Overdue Release Tasks] / [No of Release Tasks]))	Lower value is ideal
% Overdue Releases by Team	Ratio of Overdue releases associated to a team, where counting release where the team has worked on tasks for a release	NullToZero(([No of Overdue Releases by Team] / [No of Releases by Team]))	Lower value is ideal
% Successful Releases by Team	Ratio of Successful releases associated to a team, where counting release where the team has worked on tasks for a release	NullToZero(([No of Successful Releases by Team] / [No of Releases by Team]))	Higher value is ideal
Avg Release Schedule Variance Duration by Team (Days)	Average of all the schedule variances of release associated to a team where schedule variance is greater than 0, where counting release where the team has worked on tasks for a release	([Release Schedule Variance Duration By Team] / 86400)	Lower value is ideal
No of Completed Release Tasks	Count of all release tasks completed	Count([No of Completed Release Tasks])	Higher value is ideal
No of Completed Releases by Team	Count of completed tasks by a team	Max([No of Completed Releases by Team])	Higher value is ideal
No of Completed Within Time Release Tasks	Count of all release tasks completed within the stipulated time	Count([No of Completed Release Tasks]) {~} <[Release Task Within Schedule Flag = Y]	Higher value is ideal
No of Completed Within Time Releases by Team	Count of all tasks completed within time by a team	Max([No of Releases by Team]) {~} <[Release Completed Within Time by Team Flag = Y]	Higher value is ideal
No of Failed Release Tasks	Count of all failed release tasks	Count([No of Release Tasks]) {~} <[Release Task Status = FAILED]	Lower value is ideal
No of High Risk Releases by Team	Count of all high risk releases by a team	Max([No of Releases by Team]) {~} <[Release Risk By Team = HIGH]	>=0
No of Overdue Release Tasks	Count of all overdue release tasks	Count([No of Release Tasks]) {~} <[Release Task Overdue = Y]	Lower value is ideal
No of Overdue Releases by Team	Count of all overdue release tasks by a team	Max([No of Releases by Team]) {~} <[Release Overdue by Team Flag = Y]	Lower value is ideal
No of Pending Release Tasks	Count of all pending release tasks	Count([No of Release Tasks]) {~} <[Release Task Pending]	Lower value is ideal
No of Release Tasks	Count of all release tasks by a team	Count([No of Release Tasks])	>=0
No of Releases by Team	Count of releases by a team, where counting release where the team has worked on tasks for a release	Max([No of Releases by Team])	>=0
No of Resources	Count of resources associated to a team	Max([No of Resources])	>=0
No of Running Releases by Team	Count of releases by a team which are still in In-Progress, where the team has worked on tasks for a release	Max([No of Releases by Team]) {~} <[Running Releases]	>=0
No of Schedule Variance Releases by Team	Number of releases associated with a team and have schedule variance is greater than 0, where the team has worked on tasks for a release	Max([No of Releases by Team]) {~} <[Release Schedule Variance <>0]	Lower value is ideal
No of Skipped Release Tasks	Count of Release Tasks that are skipped by a team	Count([No of Completed Release Tasks]) {~} <[Release Task Status = SKIPPED]	Closer to 0 is ideal
No of Successful Releases by Team	Count of successful releases by team, where the team has worked on tasks for a release	Max([No of Releases by Team]) {~} <[Release Successful by Team Flag = Y]	Higher value is better
No of Unsuccessful Releases by Team	Count of unsuccessful releases by team, where team has worked on tasks for a release	NullToZero(([No of Releases by Team] - [No of Successful Releases by Team]))	Closer to 0 is ideal
Release Risk Score by Team	Color coding to indicate the release risk score. Red - High Risk Amber - Medium Risk Yellow - Low Risk Green - No Risk	Avg([Release Risk Score By Team])	Green is ideal